Systems and methods for protection of data across multiple users and devices

ABSTRACT

Systems and methods for protection of data across multiple users and devices are disclosed. According to one embodiment, in privacy server comprising at least one computer processor, a method for protection of data across multiple users and devices may include: (1) receiving, from a first user device, a data sharing permission for the first user device and a data sharing permission for a second user device, the first user device and the second user device associated with the same user; (2) provisioning the data sharing permission for the second user device; and (3) communicating the provisioned data sharing permission to the second user device, wherein the second user device shares data with the first user device according to the provisioned data sharing permission.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional patent ApplicationSer. No. 62/944,244, filed Dec. 5, 2019, the disclosure of which ishereby incorporated, by reference, in its entirety.

BACKGROUND OF THE INVENTION 1. Field of the Invention

Embodiments generally relate to systems and methods for protection ofdata across multiple users and devices.

2. Description of the Related Art

A service provider generally has access to data coining from multiplesources, channels and partners. That creates an array of challenges inhow data regarding the user's identity and devices that produce thepersonal data are handled, especially with regard to protecting theprivacy of such data.

SUMMARY OF THE INVENTION

Systems and methods for protection of data across multiple users anddevices are disclosed. According to one embodiment, in privacy servercomprising at least one computer processor, a method for protection ofdata across multiple users and devices may include: (1) receiving, froma first user device, a data sharing permission for the first user deviceand a data sharing permission for a second user device, the first userdevice and the second user device associated with the same user; (2)provisioning the data sharing permission for the second user device; and(3) communicating the provisioned data sharing permission to the seconduser device, wherein the second user device shares data with the firstuser device according to the provisioned data sharing permission.

In one embodiment, the data sharing permission may identify a type ofdata to share.

In one embodiment, the type of data may include account data, activitydata, preference data, etc.

In one embodiment, the first user device may be associated with a firstdevice key and the second user device may be associated with a seconddevice key, and the second device may be identified to the privacyserver by the second device key.

In one embodiment, the method may further include receiving encrypteddata from the first user device or the second user device; and storingthe encrypted data in accordance with the data sharing permission.

In one embodiment, the method may further include communicating theencrypted data to the first user device or the second user device inaccordance with the data sharing permission.

In one embodiment, the method may further include restoring theencrypted data to the same user device from which it originated.

According to another embodiment, in privacy server comprising at leastone computer processor, a method for sharing data among devicesassociated with a plurality of users may include: (1) receiving, from afirst privacy application executed on a first electronic device,registration for a first user, wherein the registration may include anidentification of the first user device and an identification of a dataowner for the data on the first user device; (2) receiving, from thefirst privacy application, data sharing preferences for the first user;(3) saving the data sharing preferences for the first user; (4)receiving, from a second privacy application executed on a secondelectronic device, registration for a second user, wherein theregistration may include an identification of the second user device andan identification of a data owner for the data on the second userdevice; (5) receiving, from the first privacy application, a request forthe second user to share data with the first user; (6) communicating therequest to the second privacy application; (7) receiving, from thesecond privacy application, a response to the request, wherein theresponse approves or denies the request; (8) configuring data sharingpermissions for the first device and the second device; and (9)communicating the data sharing permissions to the first privacyapplication and to the second privacy application, wherein at least oneof the first privacy application and the second privacy applicationupdate data sharing permissions on the respective device.

In one embodiment, the request for the second user to share data withthe first user may identify a type of data to share.

In one embodiment, the type of data may include account data, activitydata, preference data, etc.

In one embodiment, the method may further include receiving encrypteddata from the first user device or the second user device; and storingthe encrypted data in accordance with the data sharing permissions.

In one embodiment, the method may further include communicating theencrypted data to the first user device or the second user device inaccordance with the data sharing permissions.

According to another embodiment, in privacy server comprising at leastone computer processor, a method for sharing data among devicesassociated with a plurality of users may include: (1) receiving, from afirst privacy application executed on a first electronic device,registration for a first user, wherein the registration may include anidentification of the first user device and an identification of a dataowner for the data on the first user device; (2) receiving, from thefirst privacy application, data sharing preferences for the first user;(3) saving the data sharing preferences for the first user; (4)receiving, from a second privacy application executed on a secondelectronic device, registration for a second user, wherein theregistration may include an identification of the second user device andan identification of a data owner for the data on the second userdevice; (5) receiving, from the second privacy application, a requestfor the second user to share data with the first user; (6) configuringdata sharing permissions for the first device and the second device; and(7) communicating the data sharing permissions to the first privacyapplication and to the second privacy application, wherein at least oneof the first privacy application and the second privacy applicationupdate data sharing permissions on the respective device.

In one embodiment, the request for the second user to share data withthe first user may identify a type of data to share.

In one embodiment, the type of data may include account data, activitydata, preference data, etc.

In one embodiment, the method may further include receiving encrypteddata from the first user device or the second user device; and storingthe encrypted data in accordance with the data sharing permissions.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, the objectsand advantages thereof, reference is now made to the followingdescriptions taken in connection with the accompanying drawings inwhich:

FIG. 1 depicts a system for protection of data across multiple users anddevices according to one embodiment;

FIG. 2 depicts a person-level data view according to one embodiment;

FIG. 3 depicts an exemplary device-level view according to oneembodiment;

FIG. 4 depicts an illustration of sharing permission with groupsaccording to one embodiment;

FIG. 5 depicts a method for setting up sharing permissions according toone embodiment; and

FIG. 6 depicts a method for sharing data among a plurality of usersaccording to one embodiment.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments are directed to systems and methods for protection of dataacross multiple users and devices.

Embodiments may segment the user data in “Personal Data Spheres” thatenable the aggregation of data from devices that the owner may use.Embodiments may include a permission system for each device that allowsthe user to set access permissions for the data. The personal data andpermissions may be stored (e.g., as a copy) on each device and may beencrypted. The provider's server may act as a system of record and maystore both permission settings and the encrypted data that belongs tothe user for all owned devices.

In embodiments, the user's data may be encrypted with keys that are onlyknown to the user; thus, the contents are protected from the provider'sserver.

In one embodiment, permissioning may allow for segmentation of datawhere different sharing (e.g., access) permissions may be set fordifferent types of data.

Embodiments may provide some or all of the following: (1) data sharingand protection among multiple devices a user may own; (2) data sharingamong multiple users (e.g. a family or a circle of related persons); (3)data protection at-rest and in-transit; (4) flexible protection fordifferent level of data sensitivity; (5) flexible protection fordifferent tiers of data sharing according to trust or relations of ownerto other persons; (6) allowing data migration from on device to anotheror in case of data loss on device (data retrieval from server).

In embodiments, personal data (e.g., privacy data) is considered to beassociated with a person, and may be aggregated from data from devicesthat the person may own and/or control. The owner of the data may haveoverriding authority to set permissions for what to be shared with anyother entities or devices. The privacy service provider may retain thedata and share the data strictly in accordance to data owner'spermission settings.

Referring to FIG. 1 , an illustration of data spheres is providedaccording to one embodiment. FIG. 1 illustrates personal data for thePerson 1 (the owner), which may be aggregated from a plurality ofdevices, such as Device 1 and Device 2. Even though Person 1 may own orcontrol Device 3, the owner may choose not to aggregate the data fromDevice 3 (indicated by the “X”).

Within each personal data sphere (e.g., the data sphere for Person 1,Person 2, Person 3, etc.), the owner of the data (e.g. Person 1, Person2, Person 3) decides whether to aggregate each device's data andbehaviors. Data on devices that is not aggregated may be analyzed on astandalone basis. Such analysis would not combine data on non-aggregateddevices with data from any other devices, any other persons or any othersources.

Each person may have a key, such as PerKey1, PerKey2, PerKey3, and eachdevice may have a key, such as DevKey1, DevKey2, DevKey 3.

Person 2 and Person 3 may also have a plurality of devices, and mayaggregate data from their devices as illustrated. Across Personal Dataspheres, e.g., Person 2 to Owner), data may be filtered but the sourceset is the aggregated set of all participating devices. The data ownermay set sharing permissions, and such permissions may be directional(asymmetric). As illustrated, both Person 2 and Person 3 have chosen toshare data with Person 1. By Person 2 giving permission to share datawith Person 1, Person 1's data is not shared with Person 2 withoutseparate permission from Person 1. Person 2 has not decided to sharedata with Person 3, and vice-versa.

FIG. 2 illustrates a person-level data view according to embodiments.The device sharing permission may pertain only to allowing data fromparticular device(s) (e.g., Device 1 232 and Device 2 234) to be sharedwith privacy server 210 for the purposes of computing a person-leveldata view using, for example, compute module 215. For any devices thatthe owner chooses to disable sharing (e.g., Device 3 236), dataoriginated from those devices may not transit through privacy server210. Any privacy reports and scoring for such a device (e.g., Device 3236) may be computed locally on that device (e.g., Device 3 236). Thismeans that information from other sharing-enabled devices (e.g., Device1 232 and Device 2 234) belonging to the same owner and othernon-privacy information are not part of such a computation.

In one embodiment, privacy server 210 may provide a separate cloud-basedengine to compute analysis, reporting or scoring based on a data set auser chooses to submit for such computation. The user may instructprivacy server 210 whether to compute on the dataset stand-alone,combine the dataset or aggregate it with other data, and whether topersist or delete the dataset and computation results after computation.

In one embodiment, person-to-person sharing permission may pertain onlyto sharing of person-level aggregated data. This means data from adevice (e.g., Device 3 236) that is not shared with privacy server 210is not shared with another device (e.g., Device 1 232 or Device 2 234).

In one embodiment, privacy server 210 may ingest non-privacy data suchas transaction history, financial profile, etc. from one or morenon-privacy data source 225 to add intelligence to an algorithm executedby compute module 215.

For example, privacy server 210 may ingest data that may be used tofacilitate commercial transactions based on intended user experiences.In another embodiment, compute module 215 may provide data that may beused to facilitate commercial transactions based on intended userexperiences. The disclosures of U.S. Patent Application Ser. Nos.62/833,417; 16/844,560; and 16/845,937 are hereby incorporated, byreference, in their entireties.

Referring to FIG. 3 , an exemplary device-level view is providedaccording to one embodiment. Each device may include a set ofpermissions that may apply to different types of data (e.g., Type 1,Type 2, . . . Type n). Examples of different data types may includeaccounts (e.g., status, entitlements, permissions, etc.), activities(e.g., list of domains visited), and preferences (e.g., alerting,whitelisting, VPN, device fingerprint obfuscation, aliasing, scoring,etc.) on the device. These data types are exemplary only and differentdata types may be used as is necessary and/or desired.

Each data type (e.g., Type 1, Type 2, . . . Type n) may be furtherbroken down to finer grain sub-types. For example, activities may befurther broken down to activities applicable to a particular set ofdomains, such as a user may choose to share all data with the privacyserver except for data associated a healthcare provider, the IRS, etc.

Entities may identify the owner (e.g. Person 1), the server (e.g., theprivacy server), and a relations group, such as members of the samefamily. A relations group may be a user convenience feature that may beused to assign permissions to a group of entities of the same relations.

Devices may identify the devices with which the data may be shared, andmay identify those devices by Device Key (e.g., DevKey1, DevKey2, etc.).Whatever data is shared from a device for person-level aggregated viewmay be accessible by other devices.

Any access to the data generally requires sufficient permissions.

Referring to FIG. 4 , an illustration of sharing permission with groupsis provided according to one embodiment. In embodiments, any data that auser chooses to share must go through the privacy server. Thus, the usermay be the sole entity that sets sharing permissions, and the privacyserver may be the sole facilitator for data sharing based on permissionsset by the user.

As illustrated, the owner may identify where the data is saved (e.g.,server), what people to share the data with, and what devices to sharethe data with.

Referring to FIG. 5 , an exemplary method of setting up sharingpermissions is disclosed according to an embodiment.

In step 505, a data owner may set permissions for data sharing, using,for example, a data privacy application or program executed on one ofthe data owner's electronic devices.

In step 510, the permissions may be communicated to the privacy server.

In step 515, the privacy server may configure the permissions for theelectronic device(s) and may communicate the configured permissions tothe relevant electronic devices. For example, if the data owner setspermissions for device 3 to share data with device 1, the privacy serverwould configure the permissions for devices and 1 and 3 and communicatethe configured permissions to those devices. The privacy server may notcommunicate configured permissions to device 2 as there is no change fordevice 2.

In step 520, data from one or more data owner device may be acquired andstored at the privacy server. For example, if a user chooses to sharedata with the privacy server (e.g., for backup and aggregationpurposes), the privacy server may persist such data which may beencrypted according to the sharing permission set by the data owner. Thekey for decryption may be generated and persisted only on the device,precluding the privacy server from seeing the content if the data ownerchooses not to allow the privacy server to see the contents.

The keys may be stored in secure storage (e.g., keychain or EET) that isseparate from other data storage in the privacy mobile app.

Account data (such as permissions) may be stored by the privacy serveras the system-of-records, as this data is not privacy data.

Activities data (such as browsing history) may only be stored by theprivacy server if the user chooses to do so. If stored on the server,the user may retrieve/restore the data in case of device changes or dataaccidental losses.

In step 525, the data may be transmitted from the privacy server to thedevice as is necessary and/or desired. For example, if the user needs torestore the data on the electronic device, the encrypted data may bemigrated to the electronic device, decrypted, and store on theelectronic device.

Referring to FIG. 6 , a method for sharing data among devices associatedwith a plurality of users is provided according to one embodiment. Instep 605, a first user (e.g., a data owner) may enroll or register witha privacy application executed on a first user electronic device. In oneembodiment, the user may identify the user's device(s), whether the useris the owner of the data, etc.

In one embodiment, the user may identify family members, team members,etc. with which to send invitations to share data to.

In step 610, the first user may set a data sharing preference in theprivacy application. For example, the first user may identify devices,users, data, etc. that the user wishes to share with, to not share datawith, services to use (e.g., VPN, device fingerprint obfuscation,whitelisting, alerts, aliasing, scoring, etc.), etc.

In step 615, the first user's data sharing preferences may becommunicated to and saved with a privacy server.

In step 620, a second user may enroll with a privacy application on asecond user electronic device. The second user may provide anyinformation that is necessary and/or desired.

In step 625, the second user, who is in the first user's group, mayinherit the first user's data sharing preferences.

In step 630, a third user may enroll with a privacy application on athird user electronic device. The third user may provide any informationthat is necessary and/or desired.

In step 635, the first user may request permission from the third userfor the third user to share data with the first user. In one embodiment,the first user may make the request using the privacy application.

Alternatively, the third user may authorize sharing of data with thefirst user using, for example, the privacy application. In such a case,no additional permissions or authorizations are required.

In step 640, the third user may receive a notification, such as a pushnotification, an in-app message, etc. that the first user has requestedpermission, and the third user may grant or deny permission.

In step 645, if the third user grants the request, the server updatesdata sharing permissions as necessary.

If the third user denies the request, the data sharing permissions maynot be updated (e.g., they may remain unchanged). In another embodiment,the data sharing permissions may be updated to reflect that the thirduser's data is not to be shared with the first user.

In step 650, the privacy server may configure the data sharingpermissions for the first user and the third user and may communicatethe configured data sharing permissions to the first and third devicesas necessary.

In one embodiment, the device-level settings for the data sharingpermissions may override user-level preferences. For example, althoughgeneral preferences and/or permissions may be set for all of a user'sdevices, specific preferences on a device may override the generalpreferences and/or permissions.

In one embodiment, another user may request change of ownership from thecurrent owner.

Any users using a device owned by someone else would inherit the privacyservice and adhere to the sharing permission as set by the Owner.

The disclosures of U.S. patent application Ser. No. 16/598,734, and U.S.Provisional patent Application Ser. Nos. 62/856,491 and 62/874,240 arehereby incorporated, by reference, in their entireties.

Although multiple embodiments have been disclosed, it should berecognized that these embodiments are not exclusive to each other andfeatures from one embodiment may be used with others.

Hereinafter, general aspects of implementation of the systems andmethods of embodiments will be described.

Embodiments of the system or portions of the system may be in the formof a “processing machine,” such as a general-purpose computer, forexample. As used herein, the term “processing machine” is to beunderstood to include at least one processor that uses at least onememory. The at least one memory stores a set of instructions. Theinstructions may be either permanently or temporarily stored in thememory or memories of the processing machine. The processor executes theinstructions that are stored in the memory or memories in order toprocess data. The set of instructions may include various instructionsthat perform a particular task or tasks, such as those tasks describedabove. Such a set of instructions for performing a particular task maybe characterized as a program, software program, or simply software.

In one embodiment, the processing machine may be a specializedprocessor.

As noted above, the processing machine executes the instructions thatare stored in the memory or memories to process data. This processing ofdata may be in response to commands by a user or users of the processingmachine, in response to previous processing, in response to a request byanother processing machine and/or any other input, for example.

As noted above, the processing machine used to implement embodiments maybe a general-purpose computer. However, the processing machine describedabove may also utilize any of a wide variety of other technologiesincluding a special purpose computer, a computer system including, forexample, a microcomputer, mini-computer or mainframe, a programmedmicroprocessor, a micro-controller, a peripheral integrated circuitelement, a CSIC (Customer Specific Integrated Circuit) or ASIC(Application Specific Integrated Circuit) or other integrated circuit, alogic circuit, a digital signal processor, a programmable logic devicesuch as a FPGA, PLD, PLA or PAL, or any other device or arrangement ofdevices that is capable of implementing the steps of the processesdisclosed herein.

The processing machine used to implement embodiments may utilize asuitable operating system. Thus, embodiments may include a processingmachine running the iOS operating system, the OS X operating system, theAndroid operating system, the Microsoft Windows™ operating systems, theUnix operating system, the Linux operating system, the Xenix operatingsystem, the IBM AIX™ operating system, the Hewlett-Packard UX™ operatingsystem, the Novell Netware™ operating system, the Sun MicrosystemsSolaris™ operating system, the OS/2™ operating system, the BeOS™operating system, the Macintosh operating system, the Apache operatingsystem, an OpenStep™ operating system or another operating system orplatform.

It is appreciated that in order to practice the method of theembodiments as described above, it is not necessary that the processorsand/or the memories of the processing machine be physically located inthe same geographical place. That is, each of the processors and thememories used by the processing machine may be located in geographicallydistinct locations and connected so as to communicate in any suitablemanner. Additionally, it is appreciated that each of the processorand/or the memory may be composed of different physical pieces ofequipment. Accordingly, it is not necessary that the processor be onesingle piece of equipment in one location and that the memory be anothersingle piece of equipment in another location. That is, it iscontemplated that the processor may be two pieces of equipment in twodifferent physical locations. The two distinct pieces of equipment maybe connected in any suitable manner. Additionally, the memory mayinclude two or more portions of memory in two or more physicallocations.

To explain further, processing, as described above, is performed byvarious components and various memories. However, it is appreciated thatthe processing performed by two distinct components as described above,in accordance with a further embodiment, may be performed by a singlecomponent. Further, the processing performed by one distinct componentas described above may be performed by two distinct components.

In a similar manner, the memory storage performed by two distinct memoryportions as described above, in accordance with a further embodiment,may be performed by a single memory portion. Further, the memory storageperformed by one distinct memory portion as described above may beperformed by two memory portions.

Further, various technologies may be used to provide communicationbetween the various processors and/or memories, as well as to allow theprocessors and/or the memories to communicate with any other entity;i.e., so as to obtain further instructions or to access and use remotememory stores, for example. Such technologies used to provide suchcommunication might include a network, the Internet, Intranet, Extranet,LAN, an Ethernet, wireless communication via cell tower or satellite, orany client server system that provides communication, for example. Suchcommunications technologies may use any suitable protocol such asTCP/IP, UDP, or OSI, for example.

As described above, a set of instructions may be used in the processingof embodiments. The set of instructions may be in the form of a programor software. The software may be in the form of system software orapplication software, for example. The software might also be in theform of a collection of separate programs, a program module within alarger program, or a portion of a program module, for example. Thesoftware used might also include modular programming in the form ofobject oriented programming. The software tells the processing machinewhat to do with the data being processed.

Further, it is appreciated that the instructions or set of instructionsused in the implementation and operation of embodiments may be in asuitable form such that the processing machine may read theinstructions. For example, the instructions that form a program may bein the form of a suitable programming language, which is converted tomachine language or object code to allow the processor or processors toread the instructions. That is, written lines of programming code orsource code, in a particular programming language, are converted tomachine language using a compiler, assembler or interpreter. The machinelanguage is binary coded machine instructions that are specific to aparticular type of processing machine, i.e., to a particular type ofcomputer, for example. The computer understands the machine language.

Any suitable programming language may be used in accordance with thevarious embodiments. Illustratively, the programming language used mayinclude assembly language, Ada, APL, Basic, C, C++, COBOL, dBase, Forth,Fortran, Java, Modula-2, Pascal, Prolog, REXX, Visual Basic, and/orJavaScript, for example. Further, it is not necessary that a single typeof instruction or single programming language be utilized in conjunctionwith the operation of the system and method. Rather, any number ofdifferent programming languages may be utilized as is necessary and/ordesired.

Also, the instructions and/or data used in the practice of embodimentsmay utilize any compression or encryption technique or algorithm, as maybe desired. An encryption module might be used to encrypt data. Further,files or other data may be decrypted using a suitable decryption module,for example.

As described above, the embodiments may illustratively be embodied inthe form of a processing machine, including a computer or computersystem, for example, that includes at least one memory. It is to beappreciated that the set of instructions, i.e., the software forexample, that enables the computer operating system to perform theoperations described above may be contained on any of a wide variety ofmedia or medium, as desired. Further, the data that is processed by theset of instructions might also be contained on any of a wide variety ofmedia or medium. That is, the particular medium, i.e., the memory in theprocessing machine, utilized to hold the set of instructions and/or thedata used in embodiments may take on any of a variety of physical formsor transmissions, for example. Illustratively, the medium may be in theform of paper, paper transparencies, a compact disk, a DVD, anintegrated circuit, a hard disk, a floppy disk, an optical disk, amagnetic tape, a RAM, a ROM, a PROM, an EPROM, a wire, a cable, a fiber,a communications channel, a satellite transmission, a memory card, a SIMcard, or other remote transmission, as well as any other medium orsource of data that may be read by the processors.

Further, the memory or memories used in the processing machine thatimplements embodiments may be in any of a wide variety of forms to allowthe memory to hold instructions, data, or other information, as isdesired. Thus, the memory might be in the form of a database to holddata. The database might use any desired arrangement of files such as aflat file arrangement or a relational database arrangement, for example.

In the systems and methods, a variety of “user interfaces” may beutilized to allow a user to interface with the processing machine ormachines that are used to implement embodiments. As used herein, a userinterface includes any hardware, software, or combination of hardwareand software used by the processing machine that allows a user tointeract with the processing machine. A user interface may be in theform of a dialogue screen for example. A user interface may also includeany of a mouse, touch screen, keyboard, keypad, voice reader, voicerecognizer, dialogue screen, menu box, list, checkbox, toggle switch, apushbutton or any other device that allows a user to receive informationregarding the operation of the processing machine as it processes a setof instructions and/or provides the processing machine with information.Accordingly, the user interface is any device that providescommunication between a user and a processing machine. The informationprovided by the user to the processing machine through the userinterface may be in the form of a command, a selection of data, or someother input, for example.

As discussed above, a user interface is utilized by the processingmachine that performs a set of instructions such that the processingmachine processes data for a user. The user interface is typically usedby the processing machine for interacting with a user either to conveyinformation or receive information from the user. However, it should beappreciated that in accordance with some embodiments of the system andmethod, it is not necessary that a human user actually interact with auser interface used by the processing machine. Rather, it is alsocontemplated that the user interface might interact, i.e., convey andreceive information, with another processing machine, rather than ahuman user. Accordingly, the other processing machine might becharacterized as a user. Further, it is contemplated that a userinterface utilized in the system and method may interact partially withanother processing machine or processing machines, while alsointeracting partially with a human user.

It will be readily understood by those persons skilled in the art thatembodiments are susceptible to broad utility and application. Manyembodiments and adaptations of the present invention other than thoseherein described, as well as many variations, modifications andequivalent arrangements, will be apparent from or reasonably suggestedby the foregoing description thereof, without departing from thesubstance or scope.

Accordingly, while embodiments present invention has been described herein detail in relation to its exemplary embodiments, it is to beunderstood that this disclosure is only illustrative and exemplary ofthe present invention and is made to provide an enabling disclosure ofthe invention. Accordingly, the foregoing disclosure is not intended tobe construed or to limit the present invention or otherwise to excludeany other such embodiments, adaptations, variations, modifications orequivalent arrangements.

What is claimed is:
 1. A method for protection of data across multipleusers and devices, comprising: in privacy server comprising at least onecomputer processor: receiving, from a first user device, a data sharingpermission for the first user device and an initial data sharingpermission for a second user device, the first user device and thesecond user device associated with the same user; provisioning the datasharing permission for the second user device; communicating theprovisioned data sharing permission to the second user device, whereinthe second user device shares data with the first user device accordingto the provisioned data sharing permission; receiving, from the firstuser device, an updated data sharing permission for the second userdevice; determining that the updated data sharing permission for thesecond user device is different from the initial data sharingpermission; in response to the determination, communicating the updateddata sharing permission to the second user device; receiving, from thefirst user device, a third data sharing permission for the second userdevice and a third user device, the first user device and the third userdevice associated with the same user; determining that the third datasharing permission does not change the updated data sharing permissionfor the second user device; and communicating the third data sharingpermission to the third user device and not to the second user device.2. The method of claim 1, wherein the data sharing permission identifiesa type of data to share.
 3. The method of claim 2, wherein the type ofdata includes at least one of account data, activity data, andpreference data.
 4. The method of claim 1, wherein the first user deviceis associated with a first device key and the second user device isassociated with a second device key, and the second device is identifiedto the privacy server by the second device key.
 5. The method of claim1, further comprising: receiving encrypted data from the first userdevice or the second user device; and storing the encrypted data inaccordance with the data sharing permission.
 6. The method of claim 5,further comprising: communicating the encrypted data to the first userdevice or the second user device in accordance with the data sharingpermission.
 7. The method of claim 5, further comprising: restoring theencrypted data to the same user device from which it originated.
 8. Amethod for sharing data among devices associated with a plurality ofusers, comprising: in privacy server comprising at least one computerprocessor: receiving, from a first privacy application executed on afirst electronic device, registration for a first user, wherein theregistration comprises an identification of the first user device and anidentification of a data owner for the data on the first user device;receiving, from the first privacy application, data sharing preferencesfor the first user; saving the data sharing preferences for the firstuser; receiving, from a second privacy application executed on a secondelectronic device, registration for a second user, wherein theregistration comprises an identification of the second user device andan identification of a data owner for the data on the second userdevice; receiving, from the first privacy application, a request for thesecond user to share data with the first user; communicating the requestto the second privacy application; receiving, from the second privacyapplication, a response to the request, wherein the response approves ordenies the request; configuring data sharing permissions for the firstdevice and the second device; communicating the data sharing permissionsto the first privacy application and to the second privacy application,wherein at least one of the first privacy application and the secondprivacy application update data sharing permissions on the respectivedevice; receiving, from the first privacy application, updated datasharing preferences for the first user; determining that the updateddata sharing preferences alter the data sharing permissions with thesecond device; in response to the determination, updating the datasharing permissions with the second device; communicating the updateddata sharing permissions to the second privacy application; receiving,from the privacy application, a data sharing permission for the seconddevice and a third device, the first device and the third deviceassociated with the same user; determining that the data sharingpermission does not change the updated data sharing permissions for thesecond device; and communicating the data sharing permission to thethird user device and not to the second user device.
 9. The method ofclaim 8, wherein the request for the second user to share data with thefirst user identifies a type of data to share.
 10. The method of claim9, wherein the type of data includes at least one of account data,activity data, and preference data.
 11. The method of claim 8, furthercomprising: receiving encrypted data from the first user device or thesecond user device; and storing the encrypted data in accordance withthe data sharing permissions.
 12. The method of claim 11, furthercomprising: communicating the encrypted data to the first user device orthe second user device in accordance with the data sharing permissions.13. The method of claim 8, further comprising: receiving, from the firstprivacy application, second updated data sharing preferences for thefirst user; determining that the updated data sharing preferences do notalter the data sharing permissions with the second device; and inresponse to the determination, declining to communicate the secondupdated data sharing preferences to the second privacy application. 14.A method for sharing data among devices associated with a plurality ofusers, comprising: in privacy server comprising at least one computerprocessor: receiving, from a first privacy application executed on afirst electronic device, registration for a first user, wherein theregistration comprises an identification of the first user device and anidentification of a data owner for the data on the first user device;receiving, from the first privacy application, data sharing preferencesfor the first user; saving the data sharing preferences for the firstuser; receiving, from a second privacy application executed on a secondelectronic device, registration for a second user, wherein theregistration comprises an identification of the second user device andan identification of a data owner for the data on the second userdevice; receiving, from the second privacy application, a request forthe second user to share data with the first user; configuring datasharing permissions for the first device and the second device;communicating the data sharing permissions to the first privacyapplication and to the second privacy application, wherein at least oneof the first privacy application and the second privacy applicationupdate data sharing permissions on the respective device; receiving,from the first privacy application, updated data sharing preferences forthe first user; determining that the updated data sharing preferencesalter the data sharing permissions with the second device; in responseto the determination, updating the data sharing permissions with thesecond device; communicating the updated data sharing permissions to thesecond privacy application; receiving, from the first privacyapplication, a data sharing permission for the second device and a thirddevice, the first device and the third device associated with the samefirst user; determining that the data sharing permission does not changethe updated data sharing permissions for the second device; andcommunicating the data sharing permission to the third user device andnot to the second user device.
 15. The method of claim 14, wherein therequest for the second user to share data with the first user identifiesa type of data to share.
 16. The method of claim 15, wherein the type ofdata includes at least one of account data, activity data, andpreference data.
 17. The method of claim 14, further comprising:receiving encrypted data from the first user device or the second userdevice; and storing the encrypted data in accordance with the datasharing permissions.
 18. The method of claim 14, further comprising:receiving, from the first privacy application, second updated datasharing preferences for the first user; determining that the updateddata sharing preferences do not alter the data sharing permissions withthe second device; and in response to the determination, declining tocommunicate the second updated data sharing preferences to the secondprivacy application.